Summary

This PR implements route-specific middleware functionality for the REST event handler, allowing middleware to be applied to individual routes in addition to global middleware. E.g.,

// functional
const middleware1 = async (params, options, next) => {
    console.log('middleware1-start');
    await next();
    console.log('middleware1-end');
};

app.get('/test', [middleware1], (params, {event, context, request}) => {
  return { result: 'get-decorator-middleware' };
});

// decorators
@app.get('/test', [middleware1])
public async getTest() {
    return { result: 'get-decorator-middleware' };
}

Changes

Route Class (packages/event-handler/src/rest/Route.ts)

• Added middleware property to Route class constructor with default empty array

BaseRouter (packages/event-handler/src/rest/BaseRouter.ts)

• Updated all HTTP method signatures to support optional middleware parameter: get(path, middleware?, handler)
• Added overloads for decorator syntax with middleware.
• Modified resolve() method to compose global and route-specific middleware
• Route-specific middleware executes after global middleware in execution chain

RouteHandlerRegistry (packages/event-handler/src/rest/RouteHandlerRegistry.ts)

• Updated resolve() method to include middleware in returned RouteHandlerOptions

Tests

• Created factory functions for creating middlewares to reduce code duplication
• Tests for functional middleware
• Decorator tests

Issue number: closes #4430

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.